home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1994 #2
/
Monster Media No. 2 (Monster Media)(1994).ISO
/
renegade
/
ultra17.zip
/
ULTRATOP.DOC
< prev
next >
Wrap
Text File
|
1994-06-20
|
13KB
|
356 lines
── UltraTop Version 1.7 ──
(C)opyright of Killean and BeerWare Utils
── What is UltraTop?
Simply put, this program is the best top everything utility written today
for Renegade. It can handle the top 20 users of the most Posts, Calls,
Downloads, Uploads, Downloads in K, Uploads in K, best Post Call Ratios,
best Upload-Download Ratios, as well as showing the last 10 callers and
their respective info, the top 20 files downloaded from your BBS, and also
a complete user listing SIX different ways.
Well what makes this program better? Complete control of what your stat
screens will look like. I personally have never seen before a util that
you can use your own screens util now. Using my pre-determined MCI codes,
UT will act kinda like Renegade and replace the corresponding information
will the corresponding MCI code.
UltraTop is NOT a door. On my 386-40DX, it takes less than 2 seconds to
load up, generate all stats, and process 8 different ANSI screens. This
speed will easily allow you to run it as an event at night, or more
appropiately everytime a user logs off your BBS, or even as a quick drop
door. The commandline is COMPLETELY configurable to give you any option
for stat generation and more control of speed at which it operates.
── New in this version
Added new userlist sorting routine: RANK/USERNOTE order. This new option,
'+S6', will sort your user list by their SL level first, and then sort
for each level by their city/state info.
Used in conjunction with the +B parameter (use file base only), you can
now generate upload statistics for one particular file base. Syntax:
+B<name> +D
will create top number of uploads and top number of uploads in K for
file base <name>, using the regular (&N and &U) MCI set.
Another new parameter, +C<@,A-Z>, will exclude <@,A-Z> conferences from file
stat generation.
Added some better SHARE routines, so hopefully I finally fixed most of
the file conflicts.
Also, I re-wrote some of the more 'influential' routines so you should
notice a slight speed increase.
── Setup
The setup is pretty simple - edit the ULTRA.CFG text file to meet the
following criteria:
Line1 : <path to RG, i.e. C:\RG >
Line2 : <REGISTRATION #>
Line3 : <ansi text file #1> <output file #1>
or
Line3 : <header> <middle> <footer ansi> <output file #1>
| | |
Line103: <ansi text file #100> <output file #100>
The first line is just the path to your Renegade directory (backslash
doesn't matter), the second is your registration number, and the following
100 lines contain the full paths to your input ansi file and outfile files.
Not all of lines between 3 and 103 have to be used (in unregistered versions
lines after line 3 are read, but not used). A sample ULTRA.CFG file has
been provided.
Also, it does not matter what directory you run ULTRATOP from, as long as
ULTRA.CFG is in the same dir, and the RG path on line 1 is correct.
── The UT Process
First, Ultratop scans the appropiate RG data files to generate the stat
information. Next, Ultratop scans the config file for up to 100 different
input ansi files (unregistered users only get 1), reads each file looking
for MCI codes, replaces them with the corresponding data, and writes it
into the output file on the same line in the config. Pretty Simple. The
hard part is making the ansi, since the MCI codes are 4 characters long.
But I'll get to that in a sec. I have also included a few sample ansis,
already configured with the MCI codes.
The following list is the current available runtime paramters (case does
not matter):
+R - Generates the regular (top posters, top PCR, etc.) stats for the
BBS.
+L - Generates the last callers for the BBS.
+F - Generates the most downloaded files stats.
+S# - Sort users' listing by:
0: None. Retains normal user order.
1: Ascending. Sort by handle alphabetically A - Z.
2: Descending. Sort by handle alphabetically Z - A.
3: Oldest. Sort by when user first called.
4: Most Recent. Sort by date user last called, latest being
first.
5: Rank. Sort by SL alphabetically A - Z.
6: Rank/Usernote. Sort by SL and alphabetically their city/
state info.
+N - No statistics generated. User lists are still generated.
+I## - Ignore file number ## in the ULTRA.CFG list.
+O## - Use ONLY file number ## in the ULTRA.CFG list.
+Ename - Exclude filebase <name> from the filestats generation.
+Cconf - Exclude conference (@, and A through Z) from the filestats
generation.
+Bname - Use ONLY filebase <name> in the filestats generation.
+D - Generate upload stats using filebase defined from the +B
parameter.
Running Ultratop WITHOUT any of these parameters will default all three
main generation sequences, and none of the 'special' sequences. If you run
Ultratop WITH parameters, only the ones used will be generated. For
example:
Ultratop +R +L +F +EAB
will generate all three stats information using every file and excludes
any file base that has an ACS defined for conferences A and B, while
Ultratop +L +O2
will only generate the last callers information using only the second
file listed in ULTRA.CFG, and
Ultratop +S5 +ELocalAns
will sort the users' listing by RANK order and exclude filebase LOCALANS
from any filstats, but
Ultratop
will generate all three stats as well using every ansi file in the CFG,
and doesn't exlude anything or sort in any special way.
For the user listing option, UT will generate it every time it comes
across a 4 parameter line in the ULTRA.CFG file, so you could have
multiple user listings generated, but they will all be sorted the same
unless you run UT multiple times.
I implemented these parameters because the top files generation has the
possiblity of becoming a much more time consuming process than the other
two parameters, depending mainly on how many file bases you have. So
you could possibly run the last callers screen generation and various
top user screens everytime someone logs off, and then during your nightly
event generate all the screensusing different parameters.
Its all up to you.
── MCI codes
These are the current MCI codes used for UltraTop:
Name:
&P## : Top poster
&C## : Top caller
&R## : Top PCR ratio
&W## : Top number of DLs
&D## : Top DL in K
&N## : Top number of ULs
&U## : Top UL in K
&T## : Top UL/DL ratio
Each of these correspond to a second set of codes:
Data:
&p## : number of posts
&c## : number of calls
&r## : PCR ratio
&w## : number of DLs
&d## : number in K of DLs
&n## : number of ULs
&u## : number in K of ULs
&t## : UL/DL ratio
## stands for the number of the user in the list from 01 to 20, and the
uppercase codes stand for the users' Names, and the lowercase for the
users' Data.
So for example, the third Top Poster, followed by his number of posts,
would be a MCI code of:
&P03 &p03
If the '+D' parameter is used, then the '&N' and '&U' MCIs, as well as their
corresponding data '&n' and '&u' MCIs, will give the top number of uploads
and upload in K for whatever base is defined with the '+B' parameter.
Last Callers:
~B## : baud rate
~C## : city state field
~H## : handle
~N## : caller number
~T## : time logged in at
~1## : user defined answer 1
~2## : user defined answer 2
~3## : user defined answer 3
~A## : total amount of time on system
Almost same as before, the ## represents the last 01 - 10 users available
to read into your output file. I used a tilda (~) char to avoid confusion
from the other stats set.
Also, an important note for this set:
01 refers to the TENTH caller ago, and 10 refers to the MOST RECENT CALLER.
This usage enhances readability for the output file, for most lists are
produced and read from the top down. So if you were to make a ansi for
the last FIVE callers, you would start with 05 and work your way to 10 in
the input ansi file, or if you were to make a small ansi for the last caller
info, you would use 10 for replacing the ## in the code.
Top Files:
*N## : file name
*T## : number of times downloded
*W## : who uploaded it
*D## : date it was uploaded
*S## : size of the file
Again, the ## is used to represent 01 through 20 of the list of files most
downloaded. For these I used an star '*' character to search for when
generating the ansis. I had a percent '%' character before, but the new
version of renegade changed the MCI codes to that.
User Listings:
@H : users' handle
@C : users' city/state info
@1 : users' defined answer #1
@2 : users' defined answer #2
@3 : users' defined answer #3
@G : users' gender
@F : date the user was first on
@L : date the user was last on
@S : user's security level (SL)
All these codes are only a length of two characters, since it will traverse
through the USERS.DAT file generating a line for each validated user from
the MIDDLE defined ansi.
I recommend saving the MIDDLE and FOOTER ansis with a video preparation of
NONE (if you use TheDraw), and save the HEADER ansi as CLEAR. Makes sense.
---------
Most of these different stat sets (&,~,* - NOT @) can be used in a single
file, but you must remember that with the exception of the '&' stats, they
only correspond locally to each set. For example:
&U01 *N01
This is NOT the top uploader followed by the file he uploaded, but it is
the top uploader followed by the file most downloaded.
&D01 &d01 &w01
This is NOT the top downloader followed by his/her downloads in K followed
by his/her number of downloads. This example is the top downloader in K's
NAME, followed by the the top downloader in K's AMOUNT DOWNLOADED, followed
by the most number of files downloaded, almost certainly by a totally
different user than the user from &D01.
Just remember that when using the '&' codes, only the same letters, upper
and lowercase, correspond together (i.e. &D01 and &d01). For the other
sets '~' and '*', each code in the set corresponds to a SINGLE user
depending on the number in the set (##). For example:
~B10 ~C10 ~H10 ~N01 ~T10
This example IS the last caller's baud rate, followed by his city/state
info, followed by his handle (name), followed by what caller number he is,
followed by the time that he logged on. ONE user's information.
When creating your ansi file, you have to be careful of a couple of things:
First, remeber that a user's handle has a maximum length of 36 characters,
so you ought to allow room for especially long names.
Second, if you save your ansi under ansimation and save it to a particular
line length, occasionally the saving process will split the MCI codes if
it happens to land at the end of the line. To remedy this, all you have
to do is edit the ansi with a text editor and just move the codes back
together, on either line. When saving these screens, I recommend saving
them with 'None' as the output line length.
A few ansi files have been provided to give you examples to work from.
── Registration
Registration for this program is a measley 5 bucks. With this paltry
amount you get:
- Up to 100 different output files at one run
- Absense of nag lines
- Full support from the author
- 100% free updates in future
To register, send your check, along with your sysop Handle, board infor-
mation, a phone number, address, or some means of getting in touch with
you, to:
Steve Kerr
500 Northside Cir. Apt. LL-12 <------ New Address!!
Atlanta, GA 30309
If you have any questions, I can be reached at the following BBS':
Steve Kerr @
Library of Trantor BBS: 404-920-7711 (sysop: Ben Linebeck)
or
Killean @
Digital Frontier : 404-955-5073 (sysop: Cott Lang)
(or at any of the other beerware alpha sites, or my board)
Good luck,
Killean - TRiBE / BeerWare Utils